Skip to content

Conversation

BlakeLazarine
Copy link
Contributor

@BlakeLazarine BlakeLazarine commented Sep 29, 2025

The findingContext field was marked as required in Jetbrains, but was not being populated in displayFindings usages, causing the message to not be picked up as a findings message. This sent the whole json to the chat and did not populate the code issues panel.

Also, changed the language referring to /review

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Description

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@BlakeLazarine BlakeLazarine requested a review from a team as a code owner September 29, 2025 23:30
@@ -0,0 +1,4 @@
{
"type" : "bugfix",
"description" : "fix findings not being populated in the display panel"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you elaborate this to make it clear?
like Code review findings are not being populated in the display panel something like this!

@laileni-aws laileni-aws enabled auto-merge (squash) October 1, 2025 17:24
@laileni-aws laileni-aws merged commit 8424303 into aws:main Oct 1, 2025
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants